Description

When using TypeScript declarations (.d.ts files) with BridgeJS, the generated BridgeJS.Macros.swift file containing @JSFunction, @JSClass, @JSGetter, and @JSSetter declarations was not being processed by SwiftToSkeleton.

This meant that:

• Imported TypeScript APIs were missing from the BridgeJS.json skeleton
• No JavaScript glue code was generated for these imports
• The imports were unusable at runtime

Root Cause

The BridgeJSCommandPlugin filters out files from the Generated/ directory when passing input files to BridgeJSTool:

  target.sourceFiles.filter {
      !$0.url.path.hasPrefix(generatedDirectory.path + "/")
  }

Since BridgeJS.Macros.swift is generated into the Generated/ directory, it was never included in the list of files to process, even though it contains important type information that SwiftToSkeleton needs to build the imported skeleton.

Solution

After generating BridgeJS.Macros.swift from TypeScript definitions, explicitly add it to the inputFiles array before processing with SwiftToSkeleton